System and method for domain name system restore points

ABSTRACT

A system and method for domain name system (DNS) restore points are presented. A DNS record database is configured to store a plurality of DNS records for a plurality of domain name. A host computer server is configured to detect a change in a DNS record for a domain name, and, upon detecting the change in the DNS record, encode, without any user input, at least one DNS setting from the DNS record for the domain name into a data storage file. The host computer server is configured to prompt a user to provide a description, and store the data storage file containing the at least one DNS setting in a database in association with the description.

The present disclosure relates generally to systems and methods relatingto domain name system (DNS) templates and, more particularly, to thecreation and use of DNS templates, the distribution and retrieval of DNStemplates through a marketplace, and the creation of DNS setting restorepoints.

BACKGROUND OF THE INVENTION

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweenusers of computers. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information, i.e.text, graphics, sounds, and other forms of data, at specific locationson the Internet referred to as websites. The combination of all thewebsites and their corresponding web pages on the Internet is generallyknown as the World Wide Web (WWW) or simply web.

Websites may be created using HyperText Markup Language (HTML). The HTMLtags define how the web pages for the website are to be displayed. Usersof the Internet may access content providers' websites using softwareknown as a Web browser. After the browser has located the desiredwebpage, the browser requests and receives information from the webserver typically in the form of an HTML document, and then displays thewebpage content for the user. The user may then view other web pages atthe same website or move to an entirely different website using thebrowser.

In most cases, browsers are able to locate specific websites because thewebsite is hosted by a server computer having a unique Internet Protocol(IP) address. Presently, there are two standards for IP addresses. Theolder IP address standard, often called IP Version 4 (IPv4), is a 32-bitbinary number, which is typically shown in dotted decimal notation,where four 8-bit bytes are separated by a dot from each other, e.g.64.202.167.32. The notation is used to improve human readability. Thenewer IP address standard, often called IP Version 6 (IPv6) or NextGeneration Internet Protocol (IPng), is a 128-bit binary number. Thestandard human readable notation for IPv6 addresses presents the addressas eight 16-bit hexadecimal words, each separated by a colon, forexample 2EDC:BA98:0332:0000:CF8A:000C:2154:7313.

But IP addresses, even in a human readable notation, are difficult toremember and use by people. Uniform Resource Locators (URLs) are stringsof text that are easier to remember than IP addresses and may be used topoint to any website, directory or file on the Internet. A browser isable to access a website on the Internet through the use of a URL. TheURL may include a Hypertext Transfer Protocol (HTTP) request combinedwith the website's Internet address, also known as the website's domainname. An example of a URL with an HTTP request and domain name is:http://godaddy.com. In this example, the “http” identifies the URL as anHTTP request and the “godaddy.com” is the domain name.

Individuals, companies, and other entities that provide content on theweb generally want to use their name or one of their trademarks as partof their domain name. Thus, domain names are generally companytrademarks, personal names or short phrases concatenated with a toplevel domain name (TLD) extension (e.g .com, .net, org, .biz, .us, .cc,.ws, .de, etc.). TLD extensions can be divided into two groups. Thefirst group is known as generic Top-Level Domains (gTLD) and the secondgroup is country code TLDs (ccTLD).

Domain names are much easier to remember and use than theircorresponding IP addresses. The Internet Corporation for Assigned Namesand Numbers (ICANN) approves some gTLDs and delegates the responsibilityto a particular organization (hereinafter registry) for maintaining anauthoritative source for the registered domain names within a TLD andtheir corresponding IP addresses. For certain TLDs, e.g., .biz, .info,.name, and .org, the registry is also the authoritative source forcontact information related to the domain name and is referred to as a“thick” registry. For other TLDs, e.g., .com, .net, only the domain nameand name server information is stored within the registry, and aregistrar is the authoritative source for the contact informationrelated to the domain name. Such registries are referred to as “thin”registries. Most gTLDs are organized through a central domain nameShared Registration System (SRS) based on their TLD.

The process for registering a domain name with .com, .net, .org and someother registries allows a customer to use an ICANN-accredited registrar.For example, if a customer, John Doe, wishes to register the domain name“JohnDoe.com”, John Doe may initially determine whether the desireddomain name is available by contacting a registrar. The customer maymake this contact using the registrar's webpage and typing the desireddomain name into a field on the registrar's webpage created for thispurpose. Upon receiving the request from the customer, the registrar mayascertain whether “JohnDoe.com” has already been registered by checkingthe SRS database of the registry associated with the TLD of the domainname. The results of the search may then be displayed on the webpage tothereby notify the customer of the availability of the domain name. Ifthe domain name is available, the customer may proceed with theregistration process. Otherwise, the customer may keep selectingalternative domain names until an available domain name is found.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an environment in which a customdomain name may be implemented.

FIG. 2 is a screenshot showing an example user interface enabling a userto create a number of custom domain name links to third party servicesin accordance with the present disclosure.

FIG. 3 is a screen shot of the user interface of FIG. 2 after the userhas selected a button to create a custom domain name for a third partyservice.

FIG. 4 is a flowchart depicting a method for creating a DNS-based customdomain name for a third party service.

FIG. 5 is a flowchart depicting a method for creating a URLredirect-based custom domain name for a third party service.

FIG. 6 is a screenshot showing an example user interface for promptingthe user to supply the necessary tokens to create a URL redirect-basedcustom domain name.

FIG. 7 is a screenshot showing an example control panel for the DNSrecords for a domain name in which a number of records are locked.

FIG. 8 is a screenshot showing an example user interface 700 enabling auser to create a custom domain name for a third party service.

FIG. 9 is a flowchart depicting a method that may be performed by a hostupon receiving a URL entered by the user to create a custom domain namefor a third party service hosting the URL.

FIG. 10A shows a user interface for creating a DNS template fromexisting DNS settings.

FIG. 10B is a flow chart depicting a method for creating a DNS templateafter receiving a set of DNS settings.

FIG. 11 is a screenshot showing an example user interface for a user tomanage the application of a number of DNS templates to a number ofdomain names.

FIG. 12 is a flowchart illustrating an example method for applying a DNStemplate to a domain name.

FIG. 13 is a screenshot depicting an example user interface enabling auser to browse a number of available DNS templates via a DNS templatemarketplace.

FIG. 14 is a flowchart illustrating a method for updating a DNS templateand distributing those changes to the DNS records of a number of domainnames.

FIG. 15A is a flowchart illustrating a method for creating a DNS settingsnapshot in accordance with the present disclosure.

FIG. 15B is a flowchart illustrating a method for creating a DNS settingsnapshot in which additional diagnostic data is stored with thesnapshot.

FIG. 16 is a screenshot depicting an example user interface enabling auser to select a snapshot containing DNS settings and apply thosesettings to a domain name.

FIG. 17 is a screenshot depicting an example user interface enabling auser to select a snapshot containing DNS settings in which additionaldiagnostic data is displayed.

DETAILED DESCRIPTION

The present disclosure relates generally to systems and methods relatingto domain name system (DNS) templates and, more particularly, to thecreation and use of DNS templates, the distribution and retrieval of DNStemplates through a marketplace, and the creation of DNS setting restorepoints.

Once registered, a number of DNS settings are established for a domainname. The DNS settings can set forth IP addresses for the domain name,as well as for a number of sub-domain names of the primary domain name.The DNS settings can also set forth a listing of name servers to beassociated with the domain name, mail exchange (MX) records, and aliasesbetween domain names (e.g., CNAME records).

After the DNS settings have been specified for a domain name, thesettings must propagate out to a number of servers making up the DNS.This can take some time, so there may be a delay between the current DNSsettings for a particular domain name and the settings that are actuallyin effect for the domain name for any particular Internet user.

The delay in propagating DNS settings as well as the complexity of thesettings themselves, can make configuring DNS for a domain name quitedifficult and high risk. Often times, to make their domain name workwith other services, users must create a number of complex DNS settingentries for their domain name. Any error in those entries can cause oneor more services associated with the domain name (e.g., a website orInternet-based services) to operate incorrectly. In the case of a busywebsite, for example, this could result in a significant servicedisruption and possibly significant loss of business. This isparticularly true when considering the propagation delays associatedwith DNS settings. Any error or mistake in the DNS settings could takeover 48 hours to correct—24 hours to propagate the incorrect settingsand an additional 24 hours to propagate the correct DNS settings.

In many cases, a domain name can be used to reference a number ofdifferent services via the Internet or other network. This allows asingle domain name (or collection of sub-domains) to provide shortcutsor simple references to a number of different online services that mayotherwise be accessed using entirely different domain names. A singleuser, for example, having registered the domain name ‘example.com’ coulduse that single domain to receive email for the domain name‘example.com’ even if their email service hosts email for multipledomains. Similarly, the user may point their domain name (orsub-domains) to other online services, such as a blog service, a photosharing service, or an online banking service.

This arrangement both reduces the number of domains that must beremembered and recalled by the user and also enables the user's domainname to operate as a vanity or custom domain name. It allows the domainname to be used to reference services hosted by many different companiesfor many different purposes. For example, a user can use a custom domainname associated with their company to access (and allow customers toaccess) content on third party services. If the business has a primarywebsite (e.g., at ‘www.company.com’), but uses third party services toprovide some of the content on the website, such as a blog, a customdomain name (e.g., ‘blog.company.com’) may be utilized so that when avisitor accesses the company's blog content, they do so using the customdomain name, rather than the domain name of the entity hosting theblogging software.

This provides consistent branding by ensuring that the company's domainname is used through the company's website, even when customers are, infact, interacting with those third party services.

A first technique for implementing custom domain names for onlineservices involves creating DNS records that point the custom domain namedirectly to the desired third party service. This may involve creatingan A record for the custom domain name that points directly to an IPaddress of the third party service or a CNAME record that points thecustom domain name to the domain name of the third party service. Thetable below illustrates an example of an A record and a CNAME record forimplementing a custom domain via DNS entries.

TABLE 1 Name Type Value photos.example.com A 192.168.0.1blog.example.com CNAME custom.free-blog.com

In the example DNS entries depicted in Table 1, two custom domain nameentries have been created. The first links the custom domain name‘photos.example.com’ directly to an IP address—in this example, thiswould be the IP address of a third party photo sharing site. The secondentry links the custom domain name ‘blog.example.com’ directly to thedomain ‘custom.free-blog.com’, which provides a blogging service. When avisitor visits one of the custom domain names, these DNS records ensurethat the visitor's web traffic is directed to the correct third partyservice. In the case of configuring email services, a number of DNSrecords may be created that control how emails are routed to an emailservice provider. In configuring email, example DNS records may include,for example, MX records, which identify the host name of the emailservice host, as well as particular TXT records configured to enhancethe security of email services.

A second mechanism for implementing custom domain names includes the useof 301 and 302 URL redirects. URL redirection involves configuring a webserver hosting a domain name to automatically redirect a request that isissued to the custom domain name to a predetermined URL. Generally, URLredirection can be of two varieties, 301 redirects or 302 redirects. A301 redirect indicates that the redirection is permanent and causes theuser's browser, or other software receiving the redirection instruction,to permanently update its own records to indicate that the custom domainname will always point to the target URL identified by the 301 redirectmessage. Conversely a 302 redirect provides the same functionality, butindicates that the redirection is only temporary. As such, the browseror other software would not permanently update its records in responseto a 302 redirect message received from a web server.

FIG. 1 is a block diagram showing environment 100 in which a customdomain name may be implemented. Environment 100 includes a host 102.Host 102 may include a registrar providing services enabling users toregister domain names, as well as a number of other services. Forexample, Host 102 also stores a plurality of DNS records 104 andoperates as a DNS server or host. Host 102 may also provide web hostingservices and, as such, includes web server 106.

User 108 communicates with host 102 via communications network 110(e.g., the Internet). In general, user 108 communicates with host 102using a computer and suitably configured software, such as a webbrowser. User 108 may communicate with host 102 to access the domainname registry services provided by the host 102. Using those services,user 108 can search for and register a desired domain name. Onceregistered, user 108 can configure DNS settings for the domain name bychanging one or more records within DNS records 104. User 108 may alsoelect to setup a web page to be hosted at the domain name by web server106 for the domain name.

User 108 may also communicate with one or more third party serviceproviders via network 110. In the example depicted in FIG. 1, thirdparty blog service 112 allows user 108 to create an account and hostblog content with the third party blog service 112. In this example,third party blog service 112 hosts its content at the domain name‘onlineblog.com’. Blog service 112 may allow the user 108 to create andpost new content to a blog, or edit content that has already beencreated. Once submitted, the content is stored in account content 114data store (e.g., a database) and can be accessed by visitors to theblog via a suitable URL. In the present example, the blog accountcontent 114 of user 108 stored on the third party blog service 112 isaccessed via the URL http://onlineblog.com/users/accounts/user123.

Third party photo service 116 allows user 108 to create an account andstore photos, images, or other multimedia with the third party photoservice 116. In this example, third party photo service 116 hosts itscontent at the domain name ‘onlinephotostorage.com’. Third party photoservice 116 enables the user to upload and edit photographs and othermedia for redistribution via network 110. Once uploaded, images arestored within account content 118. The uploaded images can then beaccessed over the network 110 using a suitable URL. In the presentexample, the photo content of the user 108 can be accessed via the URLhttp://onlinephotostorage.com/users/accounts/example/user123.

In this example, user 108 would like to access account content 114(containing blog entries) and account content 118 (containing photocontent) using sub-domains of the domain name ‘mydomain.com’, which hasbeen previously registered with host 102. To do so, user 108 mustconfigure one of the techniques described above (e.g., creating new DNSrecords or URL redirection) for implementing a custom domain name. Thismay not be a simple process as different third party services may onlyallow the use of one technique or another.

In this example, third party blog service 112 only allows the use of URLredirects when implementing a custom domain name. As such, user 108 mustutilize either a 301 or a 302 redirect to point the custom domain name‘blog.mydomain.com’ to third party blog service 112.

This first requires that user 108 create an entry in DNS records 104 sothat the domain ‘blog.mydomain.com’ points to a web server under thecontrol of user 108. In this example, user 108 is able to modify theconfiguration of web server 106 provided by host 102. Accordingly, anentry is created in DNS records 104 pointing ‘blog.mydomain.com’ to webserver 106.

User 108 then configures web server 106 so that, in response to arequest for the domain name ‘blog.mydomain.com’, web server 106 returnsa 301 (or, alternatively, 302) redirect message pointing to the URL‘http://onlineblog.com/users/accounts/exampleuser’, which containsaccount content 114.

With both DNS records 104 updated and the 301 redirect created, thecustom domain name can be used as follows.

In a first step, user 108 (or any other visitor wishing to view the blogof user 108) enters the custom domain name ‘blog.mydomain.com’ into abrowser. The browser will then retrieve the DNS records associated withthe domain name ‘mydomain.com’ to identify the host for the domain name‘blog.mydomain.com.’ In this example, those records point to web server106.

Having retrieved the DNS records, the browser will then transmit an HTTPGET request to web server 106 in an attempt to retrieve contentassociated with the domain name ‘blog.mydomain.com.’ Web server 106receives the request, which identifies the domain name‘blog.mydomain.com’, and returns the content associated with that domainname to the user's browser. In this case, that content includes the 301redirect instruction. An example of such an instruction is presentedbelow:

HTTP/1.1 301 Moved Permanently

Location: http://onlineblog.com/users/accounts/exampleuser

Having received the 301 redirect message, the browser of user 108 willcommunicate with third party blog service 112 to retrieve accountcontent 114 stored at the URL‘http://onlineblog.com/users/accounts/exampleuser.’

This, therefore, enables user 108 or any other visitor to simply enterthe custom domain ‘blog.mydomain.com’ into a web browser to access andreceive content from third party blog service 112.

In contrast to the blog service 112, third party photo service 116allows for the use of DNS records to implement custom domains. In thisexample, user 108 would like to use the custom domain‘photos.mydomain.com’ to access account content 118 stored with thirdparty photo service 116.

This first step requires that user 108 create an entry in DNS records104 that points the custom domain ‘photos.mydomain.com’ to the thirdparty photo service 116. This may involve, for example, the creation ofan A record that points to the IP address of the photo service 116 orthe creation of a CNAME record that points to a domain name of the photoservice 116. With the necessary entry in place in DNS records 104,network traffic directed to the domain name ‘photos.mydomain.com’ willautomatically be routed to photo service 116.

Accordingly, if user 108 enters the domain name ‘photos.mydomain.com’into a browser, the browser will retrieve the DNS entry corresponding tothe domain and transmit an HTTP GET request to the photo service 116.The GET request includes a ‘Host:’ line that contains the domain name‘photos.mydomain.com.’ At this point, however, the photo service 116would ordinarily respond to the GET request by transmit a default webpage in response (i.e., a web page that does not contain account content118 of user 108). Accordingly, user 108 must also configure photoservice 116 in order to associate the domain name ‘photos.mydomain.com’with account content 118 of user 108.

To do this, user 108 accesses a user account control panel to inform thephoto service 116 that the custom domain name ‘photos.mydomain.com’should be associated with the user account of user 108. Photo service116 then stores that association in custom domain name map 120. In thisexample, because the account content 118 of user 108 is stored at theURL ‘http://onlinephotostorage.com/users/accounts/example/user’, thecustom domain name map 120 may include a table, such as Table 2 shownbelow, to store the mapping of custom domain name to user account.

TABLE 2 User Account Custom Domain Name Name Account Content URLphotos.mydomain.com user123 http://onlinephotostorage.com/users/accounts/example/user

With this mapping in place, when photo service 116 receives the GETrequest, photo service 116 can analyze the GET request to identify thecustom domain name contained in the request's ‘Host:’ line. Once thecustom domain name is identified (i.e., ‘photos.mydomain.com’), photoservice 116 can consult the records stored in custom domain name map 120to map the custom domain name to a particular user account, The accountcontent 118 associated with that user account can then be retrieved andtransmitted back in response to the request.

It is important to note that using the custom domain name approachesdescribed above, not only can user 108 utilize the custom domain namesto access the account content with both blog service 112 and photoservice 116, but anybody with access to DNS records 104 and both blogservice 112 and photo service 116 can also use the custom domain namesto access content.

The present system and method provides a domain name control panel thatenables a user to automatically configure a number of custom domainnames to point to a number of third party services. The custom domainnames can be setup and configured automatically so that when a userindicates that a particular custom domain name should be linked to aparticular third party service, the link can be created with a minimalamount of input from the user and/or work on the user's behalf.Accordingly, the present system can be configured to automaticallycreate DNS entries, 301 or 302 URL redirects, and custom domain namemaps with third party services to create the desired custom domain namelink.

FIG. 2 is a screenshot showing an example user interface 200 enabling auser to create a number of custom domain name links to third partyservices in accordance with the present disclosure. The examplepresented by user interface 200 allows a user to create a number ofcustom domain name links for the domain name ‘photoprocessing.com’.

To access user interface 200 a user provides authentication credentials(e.g., user name and password) to a registrar with whom the user hasregistered one or more domain names. After authenticating, the user canaccess a control panel to control one or more settings associated withthose registered domain names. In this example, the user has selectedthe domain name ‘photoprocessing.com’ and indicated that the user wishesto create custom domain names linking to third party services.

User interface 200 identifies the domain name 202 currently selected andfor which custom domain name links can be created. User interface 200also provides a number of buttons 204 that can be selected by the userto initiate the process of creating a third party custom domain link.Each button 204 is associated with a different third party service andprovides a simple mechanism by which the user can point a custom domainname (e.g., a sub-domain of the domain name ‘photoprocessing.com’ or thedomain ‘photoprocessing.com’ itself) to the third party service.

Depending upon the implementation, buttons 204 may include clickabletext or logos that are associated with the third party service. In somecases, however, buttons 204 may include screen shots showing an exampleweb page from the third party service. In this manner, even if the useris unaware of the name of a particular third party service, the user mayrecognize the screen shot and elect to create a custom domain name linkthereto.

In some implementations, the registrar will have access to informationassociated with the user that allows for a more intelligent selectionand depiction of the various buttons 204 enabling links to thirdparties. For example, the user's account information stored by theregistrar may indicate where the user is located. In that case, thebuttons 204 can be arranged so that third party services that areprominent nearby the user can be displayed in a more prominent position,while third party services that are less prominent can be demoted withinuser interface 200.

In another example, the user's account information may identify abusiness or entity type or category for the user. For example, theuser's account may be affiliated with a business. In that case, theuser's account may indicate the type of business (e.g., bakery, bikeshop, law firm, and the like). With the business type identified, thebuttons 204 can be arranged so that third party services that are morerelevant to the business type are display in a prominent position, whileless relevant third party services are demoted.

For example, if the user is affiliated with a bakery or restaurant, thebutton 204 that allows the user to create a custom domain name for aYELP account may be made more prominent. Conversely, if the user isaffiliated with a photography service, a button 204 enabling the user tolink to a photo sharing site (e.g., FLICKR) may be made more prominent.Similarly, if the user is unaffiliated with a business, buttons 204associated with third party services that are more relevant to personalweb sites may be given more prominence (e.g., PINTEREST and WEDDINGWIRE).

In other embodiments, buttons 204 may be prioritized to make somebuttons 204 more prominent based upon other factors or variables, suchas the prior purchases or product usage history of the user or theuser's prior use of some third party services. In some cases, thirdparties may compensate host 102 for displaying some buttons 204 in moreprominent positions that others.

In this disclosure, a more prominent placement location for a button 204may comprise any location in the listing of buttons 204 depicted withinuser interface 200 that may be more likely to attract the attention of auser using user interface 200 than another location. The prominentplacement location, as non-limiting examples, may be determined by humanfactors, usability, or similar studies, or may be a simple arbitrary orintuitive choice. As illustrated by user interface 200, it also maycomprise a preferred placement of a button 204 within a verticalarrangement of a plurality of buttons 204, perhaps at the top of a listof buttons 204, or simply a higher placement within such a list than theplacement of other buttons 204. The preferred placement may therefore,as non-limiting examples, comprise a top-most, bottom-most, or morecentered position in any such vertical list.

In some embodiments, user interface 200 may include one or more buttons204 or other user interface mechanisms enabling the user to createcustom domain name links between domain names that are registered to theuser. For example, if the user has registered the domain namescompanyname.com and companyname.co, one or more buttons 204 may beincluded in user interface 200 enabling the user to forward the .codomain name to the .com domain name (assuming that the .com domain nameis already tied to accessible user content) so that Internet trafficthat is initially directed to the .co domain name is automaticallyrouted to the .com domain name instead. Additionally, one or morebuttons 204 may be made available allowing the user to pointcompanyname.blog to a specific URL, such as companyname.com/blog, ifcontent is detected at that URL.

To enable the operation of user interface 200, host 102 stores, for eachthird party service that may be linked to (e.g., for each button 204),information describing how such link is to be created in a third partyservice link database. This may involve, for each third party serviceprovider, storing data indicating whether the third party service allowsDNS-based custom domain names, or relies on 301 or 302 redirects. Thedata will further include, for each technique of creating a customdomain name link, the specific details of how such a custom domain namelink is to be created. For example, the data may include a listing ofDNS records that must be created to enable the custom domain name linkto operate. The data may also include a listing or description ofuser-specific data that must be retrieved from the third party serviceprovider and inserted into a DNS record before the custom domain namelink will function correctly.

For services that support DNS-based custom domain names, host 102 maystore the following information depicted in Table 3 in the third partyservice link database.

TABLE 3 Data Description Name The name of the third party serviceMobile? Indicates whether the third party service is hosting websitecontent formatted for display on a mobile device - yes/no value. DNStemplates Defines a number of templates for DNS records that (type andvalue) must be created to implement the custom domain name link. The DNSrecord templates may be static entries that specify a name, type (e.g.,A or CNAME) and value (e.g., a known IP address or domain name). Thetemplates may include variables that must be replaced by user-specifictokens. Region Indicates a geographical region for the third partyservice Authentication Specifies an authentication mechanism that thehost Mechanism 100 can use to access the third party service to createand modify custom domain name map records stored with the third partyservice as well as retrieve user- specific tokens from the third partyservice(e.g., OAuth) Default? Indicates whether this entry is thedefault entry for the third party service

For services that support 301 or 302 URL redirects for custom domainnames, host 102 may store the following information depicted in Table 4in the third party service link database.

TABLE 4 Data Description Name The name of the third party serviceMobile? Indicates whether the third party service is hosting websitecontent formatted for display on a mobile device - yes/no value. URLRedirect Stores a template for the URL that will be entered intotemplate the URL redirect - may include variables that are filled in atthe time of creation with information provided by the user (e.g.,https://www.service.com/users/accounts/home/[account name]) Token(s)Identifies each of the tokens we need from the user in order to be ableto create the URL redirect (e.g., account name, account nickname,account number, etc.) 301 or 302 URL Indicates whether the redirectshould be implemented redirect? as a 301 or 302 redirect RegionIndicates a geographical region for the third party service Default?Indicates whether this entry is the default entry for the third partyservice

For services that provide email services, host 102 may additionallystore MX records and sender policy framework (SPF) details for theservice in the third party service link database.

The third party service link database (e.g., the records described aboveand in Table 3 and Table 4) may be stored by host 102 in any suitablestorage location and format. For example, the records may be stored in adatabase, such as a relational database (e.g., PostgreSQL, ORACLEdatabase, MICROSOFT SQL SERVER) configured to store the third partyservice link database accessible to host 102. The database may be localto (e.g., running on) host 102, or may be hosted by a server computerremote to host 102 and accessible using network 110. The third partyservice link database may be stored, for example, in one or more tablesof a relational database (e.g., database 107 of FIG. 1). Alternatively,the records may be stored in tables or text files on any suitable datastorage device accessible to host 102. In various embodiments, therecords may store additional information such as an “Activation Rate”which indicates how many users are setting up that type of custom domainname. The records may also store a cost value, should a monetary fee orcost be associated with a particular type of custom domain name.

Returning to FIG. 2, to create a custom domain name for a third partyservice, the user first selects one of buttons 204 on user interface 200provided by host 102. After the user selects one of buttons 204,indicating that the user wishes to create a custom domain name for thethird party service associated with that button 204, host 102 identifiesthe third party service associated with the button 204 selected by theuser.

With the third party service selected and identified, host 102 thenprompts the user to enter a custom domain name to be linked to theselected third party service. The custom domain name, for example, maybe a sub-domain of the domain name for which settings are currentlybeing modified (e.g., photoprocessing.com in FIG. 2) or the domain nameitself. Accordingly, the custom domain name may be a second level domainname (SLD), n-level domain (nLD), or any other form of domain name. FIG.3, for example, shows a screen shot of user interface 200 after the userhas selected one of buttons 204 to create a custom domain name for athird party service. As illustrated, the user is prompt with form 302 tosupply the desired custom domain name to be linked to the selected thirdparty service. Although the example depicted in FIG. 3 shows the userbeing able to enter a sub-domain to the domain name‘photoprocessing.com’ as the custom domain name, the user may insteadelect to not enter a sub-domain and use the domain name‘photoprocessing.com’ for the custom domain name.

After the user enters the custom domain name (in this example,‘blog.photoprocessing.com’), the host 102 looks up the selected thirdparty service in the third party service link database to determinewhether the selected third party service allows DNS-based custom domainnames. If the selected third party service allows DNS-based customdomain names, the host 102 may perform the method illustrated in FIG. 4to create the user's desired custom domain name.

Referring to FIG. 4, in step 402 host 102 accesses the third partyservice link database to retrieve the entry for the selected third partyservice. In some cases, where there are multiple entries for theselected third party service, this will involve selecting the entry thatis associated with a location that matches that of the user. In thisoptional step, the location of the user may be identified, for example,by examining the customer records of the user (e.g., to identify amailing address or residence address for the user), or analyzing an IPaddress of the user to determine a location of the user's computer.Then, the entry for the selected third party service with a region thatencompasses that of the user can be retrieved. In the event that noentry includes a region that encompasses the user, one of the entriesfor the selected third party service may be defined as a default entryto be utilized.

In some cases, the custom domain name provided by the user will at leastpartially determine which entry is retrieved for the selected thirdparty service. For example, if the custom domain name entered by theuser is ‘mobile.photoprocessing.com’ or ‘m.photoprocessing.com’, the useof the terms ‘mobile’ or ‘m’ may indicate that the user wishes to usethe custom domain name to display content suited for display on a mobiledevice. In that case, host 102 would retrieve the entry for the thirdparty service that is designated as being mobile, should one exist. Thehost 102 may make this selection automatically, or may prompt the userto confirm that the custom domain name is for mobile content.

Once the entry is retrieved for the selected third party service, instep 404 host 102 analyzes the DNS templates stored in the entry. Asdescribed above in reference to Table 3, the DNS templates may includestatic entries as well as entries that contain variables. The statictemplates will generally set forth a type as well as a value for thetemplate. Example static entries may have a type of ‘A’ and a valueincluding an IP address (e.g., ‘123.123.123.123’), for example.Similarly, a static entry may have a type of ‘CNAME’ and a value of adomain name (e.g., ‘domains.blogtool.com.’).

For the records that are static, host 102 creates a DNS record (e.g.,within DNS records 104) for each static record using the data from theentry and the user's desired custom domain name. If the templateincludes an IP address for the selected third party service, host 102may create an A record within DNS records 104 that points the customdomain name to the IP address. Alternatively, if the template includes adomain name for the third party service, host 102 may create a CNAMErecord within DNS records 104 that points the custom domain name to thedomain name for the third party service. In some embodiments, step 404may involve host 102 modifying one or more customer records of the userso that DNS records 104 become the controlling DNS records for theuser's domain name.

In some cases, however, the DNS templates may include entries thatcontain variables. This may be the case, for example, if the third partyservice requires an individual attempting to utilize a custom domainname with the third party service to enter a specific token or code intoa DNS record as a means of authenticating that the user has theauthorization to create the custom domain name link. These tokens may bestrings of characters that must be entered into the DNS record or mayinclude some information known to the user, such as their userid withthe third party service. Before the variable templates can beinstantiated as DNS records, the variables must be replaced by thesuitable token for the user. For example, a variable record in a DNStemplate may specify a type of ‘TEXT’ and a value of“photoblog-{token}”, where {token} denotes a variable that must bereplaced by some security token. For example, the security token for aparticular user may be ‘XYZ567’. In that case, the variable templatewould be used in combination with the security token to create a DNSrecord of type TEXT and having a value of ‘photoblog-XYZ567.

If the DNS templates include variables, corresponding DNS records cannotbe generated in step 404 because the security tokens are unknown. Assuch, only DNS records for the static templates will be created in step404.

In step 408, host 102 accesses the third party service to both setup thecustom domain name mapping to the user's account and also, if any of theDNS templates for the third party service include variables, request thenecessary security tokens. As mentioned above, the security tokens mayinclude strings of characters or other information such as the user'saccount name or ID with the third party service.

Host 102 may use any suitable mechanism to access the third partyservice to both create custom domain name mappings as well as toretrieve security tokens. In one embodiment, host 102 relies upon accessmechanisms that are delegated to the host 102 from the third partyservice, such as OAuth. Alternatively, host 102 may prompt the user forthe user's security credentials (e.g., username and password) for thethird party service. After the user provides the security credentials,host 102 can use those credentials to access the third party service tosetup the custom domain name mapping to the user's account with thethird party service in step 410. The third party service may also offeran application program interface (API) through which host 102 can createor modify a custom domain name map after supplying the appropriatesecurity credentials and retrieve security tokens.

If the authentication process described herein should fail, the presentsystem may be configured to display helpful ‘next steps’ to assist theuser in completing the activity manually. These next steps may be storedin the custom domain name link database described above, as the manual‘next steps’ may be different for each third party service.

In some other embodiments, however, rather than host 102 prompting theuser for authentication credentials and then communicating directly withthe third party service provider, step 408 includes host 102 simplyproviding the user with instructions on how to create the custom domainname mapping with the third party service manually.

In step 410, if any of the DNS templates for the third party serviceincluded variables, those variables can be replaced by the securitytoken retrieved in step 408 and the corresponding DNS records can becreated.

Once the custom domain name mapping has been created at the third partyservice to link the custom domain name with the user's account and theDNS records have been created, in step 412 the user can be notified thatthe custom domain name has been correctly setup for the third partyservice.

If, however, the selected third party service requires URL redirects toimplement custom domain names, host 102 may perform the methodillustrated in FIG. 5 to create the user's desired custom domain namelink.

In step 502, host 102 accesses the third party service link database toretrieve the entry for the selected third party service. In some cases,where there are multiple entries for the selected third party service,this will involve selecting the entry that is associated with a locationthat matches that of the user. In this optional step, the location ofthe user may be identified, for example, by examining the customerrecords of the user, or analyzing an IP address of the user to determinea location of the user's computer. Then, the entry for the selectedthird party service with a region that encompasses that of the user canbe retrieved. In the event that no entry includes a region thatencompasses the user, one of the entries for the selected third partyservice may be defined as a default entry to be utilized.

In some cases, the custom domain name provided by the user will at leastpartially determine which entry is retrieved for the selected thirdparty service. For example, if the custom domain name entered by theuser is ‘mobile.photoprocessing.com’ or ‘m.photoprocessing.com’, the useof the terms ‘mobile’ or ‘m’ may indicate that the user wishes to usethe custom domain name to display content suited for display on a mobiledevice. In that case, host 102 would retrieve the entry for the thirdparty service that is designated as being mobile, should one exist. Host102 may make this selection automatically, or may prompt the user toconfirm that the custom domain name is for mobile content.

Once the entry is retrieved for the selected mobile service, in step 504host 102 creates a DNS record (e.g., within DNS records 104). In thiscase, the DNS entry will point the custom domain name supplied by theuser to a web server under the control of host 102 (e.g., web server106).

With the DNS record created, in step 506 host 102 prompts the user toprovide the one or more tokens necessary for the creation of the URLredirect. In many cases, this will be a single token that includes auser name or other user account identifier. FIG. 6 is a screenshotshowing an example user interface for prompting the user to supply thenecessary tokens to create a URL redirect.

Returning to FIG. 5, after the user has supplied the required tokens, instep 508 host 102 constructs a URL redirect using the supplied tokensand the Redirect URL Template retrieved from the third party servicelink database. This involves replacing the variables in the templatewith the tokens that were provided by the user. In an example, a URLredirect is being created for a third party service that has the URLRedirect Template of‘https://www.service.com/users/accounts/home/[account name]’. The userhas provided an account name of ‘photos_123’. In that case, the accountname would be inserted into the URL Redirect Template so that the URLredirect becomes ‘https://www.service.com/users/accounts/home/photos_123’.

Host 102 can then create the URL redirect and install the URL redirecton web server 106. This may involve, for example, modifying one or moreconfiguration files (e.g., .htaccess files) within web server 106 orusing another configuration mechanism to setup and implement the URLredirect. With the URL redirect installed on web server 106, the customdomain name has been created. Accordingly, in step 510, the user can benotified that the custom domain name has been correctly setup for thethird party service.

In situations where the third party service provided email services,host 102 may be configured to retrieve MX and SPF records for the thirdparty service from the third party service link database. Once received,those MX and SPF records may be utilized to automatically configure thethird party service to host email services for the custom domain name.

In some embodiments, once the custom domain names have been implemented(e.g., using the method of either FIG. 4 or FIG. 5), host 102 mayprovide the user with a preview of the operation of the custom domainname (e.g., by popping up a browser window directed to the custom domainname) to provide the user with an opportunity to confirm the successfuloperation of the custom domain name. If the user is happy with thecustom domain name's operation, the custom domain name (and thecorresponding DNS, web server, and third party service settings) can bemade permanent. Alternatively, if the user is not happy with the customdomain name's operation, the changes can be cancelled allowing the userto setup the custom domain name differently.

Once a custom domain name has been created for the user, the user willbe able to access a configuration tool for their domain name's DNSsettings and view the new entries that were created by host 102 toimplement the custom domain name.

In the present system, the DNS entries that were created as a result ofthe creation of a custom domain name (e.g., via the performance of themethods of FIG. 4 or FIG. 5), may be locked so that they cannot beedited or revised by the user. This can provide at least two benefits.First, the DNS entries can be complicated—even relatively minor errorsin the DNS records for a particular domain name could result in thedomain name (and its sub-domains) not operating as desired. As such, thelocking of those DNS entries prevents inadvertent errors being created,which may render the custom domain names inoperative. Second, althoughthe domain name entries are locked to the user, they can still be editedby host 102. This allows host 102 to update the entries when changes aremade the third party service link database. For example, if the IPaddress associated with a third party service changes in the third partyservice link database, host 102 can automatically update all DNS entriesthat have been created for users in DNS records 104 for that third partyservice.

Similarly, if a third party service switches from a URL redirect-basedcustom domain approach to a DNS-based approach, host 102 canautomatically update the settings of users who have previouslyimplemented URL redirect-based custom domain names for that third partyservice.

To illustrate, FIG. 7 is a screenshot showing an example control panelfor the DNS records for a domain name in which a number of records arelocked. Referring to FIG. 7, the DNS records for the domain name‘photoprocessing.com’ are presented. As illustrated the user interfaceincludes a number of DNS records 650 for the domain name. The records inthis example include an A record entry and an MX (mail) entry.

As indicated by icon 652, the A record has been created to implement acustom domain name link to the third party application TUMBLR. Thatrecord, then is locked and cannot be edited by the user. Instead, theuser is only presented with the option to delete the custom domain namelink using button 654. Similarly, as indicated by icon 656, the MXrecord and any other corresponding DNS records required to implement theemail services have been created to implement a custom domain name linkto the third party application OFFICE365. Those records are then lockedand cannot be edited by the user. Instead, the user is only presentedwith the option to delete the custom domain name link using button 658.

In the system described above, settings are stored in a third partyservice link database enabling the automatic (or semi-automatic)creation of custom domain names for a number of different third partyservices.

In some implementations, the user may want to create a custom domainname for a third party service for which the user cannot identify aspecific button 204. In that case, the user may select the button 206 tocreate a custom domain name for a third party service of ‘other’. Oncethe user has selected that button, they are presented with the userinterface depicted in FIG. 8.

FIG. 8 is a screenshot showing an example user interface 700 enabling auser to create a custom domain name for a third party service. After theuser has selected the button for the ‘other’ third party service, theuser is presented with a text box 702 allowing the user to paste a URL.The URL pasted into text box 702 will be a URL pointing to the thirdparty service for which the user wishes to create a custom domain name.

For example, if the user wishes to create a custom domain name toreference a particular website on a third party service (e.g.,‘http://www.ebay.com/stores/samples), the user would paste that URL intotext box 702. With the URL pasted into text box 702, the user can pressthe finish button 704 to submit the URL to host 102 and initiate theprocess of creating a custom domain name for the URL. FIG. 9 is aflowchart depicting a method that may be performed by host 102 uponreceiving the URL entered by the user to create a custom domain name forthe associated third party service.

Referring to FIG. 9, in step 802 the URL submitted by the user isreceived. In step 804, the URL can be parsed to identify the third partyservice. This involves identifying the SLD in the submitted URL, whichwill generally identify the third party service. In the present exampleURL of ‘http://www.ebay.com/stores/samples’, the third party servicewould be identified as ‘ebay’. In this step, the URL is further parsedto identify any sub-domain that may be identified in the URL. In thisexample, the sub-domain is ‘www’, though other sub-domains such as‘mobile’ or ‘m’ may be identified within the URL.

In step 806, the user is prompted to provide a custom domain name forthe third party service. In some cases, the user may be provided with ablank form in which to enter the custom domain name (see, for example,form 302 on FIG. 3). In other cases, however, the custom domain name maybe pre-populated based upon the parsing of the URL performed in step 804or, alternatively, step 806 may be option and the user's domain name maybe utilized directly as the custom domain name. The custom domain name,for example, may be pre-populated with the name of the serviceidentified in step 804. In that case, in the present example the customdomain name suggested may be ‘ebay.photoprocessing.com’.

After the user has either provided the custom domain name or acceptedthe suggested custom domain name, in step 808 a search is performed todetermine whether an entry is provided for the third party service inthe third party service link database, described above. Thisdetermination may be made, by identifying whether one or more entriesexist where the name defined in the third party service link database isequal to the name of the third party service identified in step 804.

If so, then the appropriate entry is selected and a custom domain namelink is created accordingly in step 814. This may involve, for example,the execution of one of the methods shown in FIG. 4 and FIG. 5 anddescribed above. In this step, if a sub-domain of ‘mobile’ or ‘m’ wasidentified in the URL, then a mobile entry for the third party servicein the third party service link database would be used, if available.

If, however, an entry does not exist in the third party service linkdatabase for the third party service, in step 810, host 102 may beconfigured to analyze all available records in DNS records 104 and allURL redirects created on web server 106 in order to identify a preferredmechanism for creating custom domain names to the third party service.If, as a result of this analysis, host 102 determines that there are alarge number of URL redirects pointing to the third party service, thatmay indicate that the third party service does not accept DNS-basedcustom domain names. In that case, the method may move to step 814 wherea custom domain name link is created using a URL redirect that pointsthe custom domain name provided by the user in step 806 to the URLreceived from the user in step 802.

Conversely, the analysis performed in step 810 may determine that thereare a large number of DNS entries pointing to the third party service,with relatively few URL redirects pointing to the third party service.That may indicate that the third party service accepts DNS-based customdomain names. In that case, the method may move to step 814 where aDNS-based custom domain name is created and the user is prompted toaccess the third party service to create the appropriate custom domainname mapping.

Finally, in step 812, if no suitable mechanism has been identified forcreating a custom domain name link to the third party service, a URLredirect may be created to point the custom domain name to the URLreceived in step 802.

In addition to creating custom domain name links, the present systemallows for the creation of DNS templates that can set forth a number ofDNS settings that can be associated with a particular domain name. Oncecreated, a DNS template can be applied to one or more domain names, anduploaded to and distributed through an Internet-accessible repository,such as a DNS template marketplace. In some cases, the DNS templatesystem, as described below, can be utilized to create or define DNSsettings snapshots allowing the DNS settings associated with aparticular domain name to be reverted to a prior set of settings.

A DNS template may set forth all DNS settings associated with aparticular domain name (in some cases, referred to as a DNS zone). Inother cases, however, a DNS template may only set forth a subset of DNSsettings that may be specified for a particular domain name. Forexample, a DNS template could be created to specify a single A recordpointing a domain name to an IP address. An example of this could be aDNS template that sets forth a link between a domain name beginning with‘photos.’ to a particular IP address. Such a template could be used by aphoto sharing website, for example, to define how users can link theirdomain name to the photo sharing website. An example of such a DNStemplate follows:

[DNS Template - Photo Sharing] photos IN A 192.168.0.3

In some cases, the DNS templates could specify a number of different DNSsettings for a particular domain name. For example, a DNS template couldbe created that specifies a number of MX records that can be used toconfigure a domain name for email delivery. An example of such a DNStemplate follows:

[DNS Template - Email Hosting] @ 3600 MX  1 mail1.emailhosting.com @3600 MX  5 mail2.emailhosting.com @ 3600 MX  5 mail3.emailhosting.com @3600 MX 10 mail-alternate.emailhosting.com

In some cases, DNS templates can be created that provide a comprehensiveset of DNS settings for a domain name. For example, the followingexample DNS template contains DNS settings to specify IP addresses for anumber of subdomains, a domain name alias, MX records for emailservices, and a number of name servers.

[zone template - business software suite] accounting IN A 192.168.0.3 hrIN A 192.168.0.4 www IN A 192.168.1.158 www-beta IN CNAME www @ 3600 MX1 mail1.emailhosting.com @ 3600 MX 5 mail2.emailhosting.com @ 3600 MX 5mail3.emailhosting.com IN NS 192.168.1.1 IN NS 192.168.1.2

In some embodiments, a number of DNS templates (e.g., a set of DNStemplates) could be applied in combination to apply settings to a domainname root as well as related subdomains. Because each subdomain may havean individual zone file, the set of DNS templates could set up thesubdomains and root appropriately.

The DNS templates, once created, may be stored in any suitable format.In one embodiment, the DNS templates may be stored as text documentsusing similar formatting requirements to those established forconventional DNS records. Alternatively, the DNS templates may be storedin a marked-up format, such as using eXtensible Markup Language (XML) oranother format and stored within a suitable data storage device.

In one embodiment, a DNS template can be created by a user from DNSsettings established in an existing zone file associated with anoriginal domain name. For example, a user, having configured a number ofDNS settings for the original domain name may want to use those settings(or at least a subset of those settings) to create a DNS template. ThatDNS template, once created, could then be applied to the DNS settingsfor a number of other domain names to quickly and accurately duplicateDNS settings across a number of domain names.

As an illustration, FIG. 10A shows a user interface 1000 for creating aDNS template from existing DNS settings. In the example depicted in FIG.10A, a user wishes to create a DNS template from DNS settings associatedwith the original domain name ‘example.com’. To create the DNS template,the user accesses a software application provided by, for example, host102, The application retrieves the current DNS record for the domainname ‘example.com’ and display the contents of the record in userinterface 1000. This may involves parsing the DNS record for the domainname into a number of different DNS settings. The DNS record may beparsed so that each individual record is designated as a separate DNSsetting. The DNS record may be retrieved by host 102, for example, fromDNS records 104, shown on FIG. 1.

After the records have been displayed in user interface 1000, the useris provided with a number of user interface elements 1002 enabling theuser to select one or more of the individual settings depicted in userinterface 1002. In the example shown in FIG. 10A, each setting ispresented on a separate line and user interface elements 1002 includecheckboxes, though any other suitable user interface element may beutilized to enable the user to provide a selection of one or more of thesettings in the DNS record via user interface 1000.

As illustrated in FIG. 10A, the user has selected settings that setforth a particular set of name servers for the domain (the NS records),as well as a number of IP addresses (the A records) and aliases (theCNAME records) for a number of subdomains.

After the user has selected the settings from the DNS records that areto be placed into the DNS template, the user activates button 1004 toinitiate DNS template creation. After the user activates button 1004,the DNS records selected by the user are analyzed and placed into a DNStemplate for later use, as described below.

FIG. 10B is a flow chart depicting method 1050 for creating a DNStemplate based upon a set of DNS settings selected by a user. The methodmay be executed, for example, by host 102 after the user has activatedbutton 1004 shown in FIG. 10A.

In step 1052, the list of the items selected in the DNS settings (see,for example, FIG. 10A) are received from user interface 1000. The listmay include the settings directly, or may include a number of referencesto storage locations (e.g., within DNS records 104) from which thesettings can be retrieved.

With reference to the example depicted in FIG. 10A, step 1052 involvesreceiving the following listing of items from the DNS record associatedwith the original domain name ‘example.com’:

example.com. IN NS ns example.com. IN NS ns.somewhere.example. www INCNAME example.com. wwwtest IN CNAME www mail IN A 192.0.2.3 accounts INA 192.0.2.4

In addition to receiving the selected DNS settings, in step 1052, thedomain name originally associated with the settings (i.e.,‘example.com’) is also received.

Because some of the DNS settings received in step 1052 are specificallytailored to work with the domain name ‘example.com’ the method involvesstripping the original domain name from the settings. This makes thesettings generic and suitable for application to other domain names andgenerally involves replacing the original domain name with a variable(e.g., a text string) that can then later be replaced by a new domainname when the DNS template is used to create DNS settings for the newdomain name.

This is generally the case for all instances where the original domainname appears in the DNS settings, except where the original domain nameappears as a specified nameserver or mailserver (e.g., as the value inan NS setting or MX setting). In some cases, the DNS settings may use acharacter such as ‘@’ to refer to the primary domain name associatedwith the DNS settings. In that case, the ‘@’ character may be retained(i.e., left unchanged) when the DNS template is created. Alternatively,in some embodiments, instances of the domain name may be replaced withthe variable ‘@’ in the DNS template.

Accordingly, in step 1054 the DNS settings received in step 1052 areanalyzed to identify instances of the domain name originally associatedwith the settings (except where the domain name appears as a specifiednameserver or mail server). Then, in step 1056, the instances of thedomain name identified in step 1054 are replaced with a suitablevariable. In the present example, the variable will be the string‘[domain name]’, though any suitable variable may be utilized. It isonly necessary that the variable, at a later time, can be replaced by adifferent domain name to create a set of DNS settings for that domainname, as described below.

As such, with reference to the present example, after performing step1056, the DNS settings will be as follows:

[domain name]. IN NS ns [domain name]. IN NS ns.somewhere.example.com.www IN CNAME [domain name]. wwwtest IN CNAME www mail IN A 192.0.2.3accounts IN A 192.0.2.4

It is apparent, therefore, that in all instances the original domainname ‘example.com’ has been replaced by the variable ‘[domain name]’,except where the domain name ‘example.com’ is a specified nameserver ormail server in the DNS settings. The modified DNS settings can then beincorporated into a DNS template in step 1058.

After the DNS template has been created in step 1058, the DNS templatecan be stored in any suitable computer-readable medium in a DNS templatedatabase, such as in database 107, which is accessible to host 102, instep 1060 for later use. Step 1060, which involves the storing of theDNS template, may also involve receiving from the user a suitabledescriptive name for the DNS template. The descriptive name can bestored in conjunction with the DNS template to facilitate retrieval anduse by a user at a later time.

In some embodiments, instead of requiring that the user select one ormore DNS settings for a particular domain name in order to create a DNStemplate, the user may instead be presented with the option of selectingone or more categories of DNS settings for incorporation into a DNStemplate. With reference, to FIG. 10A, for example, instead of beingpresented with an opportunity to select each individual DNS setting, theuser may instead be presented with the option of selecting thecollection of name server records, mail records, A records, and/or CNAMErecords for incorporation into a DNS template. This approach maysimplify the user interface for the user making it easier to identifythe desired records for the DNS template.

In some cases, the system may automatically select which DNS settingsare to be incorporated into the DNS template, and may, therefore, createa DNS template for the DNS settings of a particular domain name withoutany selection of particular settings by a user. For example, the systemmay be configured so that a user, when viewing the DNS settingsassociated with a particular domain name, can create a DNS template witha single user input. In such an embodiment, the system may be configuredto create a DNS template using all A and CNAME records for the domainname, but to ignore nameserver and MX records, for example.Alternatively, a user may create a DNS template by selecting apre-ground category of DNS settings (e.g., all DNS settings associatedwith the web service TUMBLR).

Once the DNS template has been created and stored, the user can managethe DNS template, which may involve applying the template to one or moreother domain names registered by the user. FIG. 11 is a screenshotshowing an example user interface for a user to manage the applicationof a number of DNS templates to the DNS settings for a number of domainnames.

User interface 1100 may be generated, for example, by a softwareapplication running on host 102 and shows a number of settings andoptions associated with the domain names registered to a particularuser. User interface 1100 includes window 1102 that displays a listingof domain names that are registered to the user. In this example, theuser has selected one of the domain names, as indicated by selectiongraphic 1108.

Window 1104 display a listing of DNS templates that have been applied tothe domain name selected in window 1102. In this example, the user hasselected the domain name ‘smith-family-blog.net’. The DNS templatesactive for that domain name are shown in window 1104 and include thetemplate ‘Free Email Hosting—Mail Settings’, which may include a numberof DNS settings associated with providing email services, the template‘Blog with Free Blog Tools’, which may include a number of DNS settingsenabling the user to host a blog, and the template ‘Free Photo Hosting’,which may include a number of DNS settings enabling the user to utilizea free online photo hosting site.

Window 1104 includes button 1106, which enables a user to remove a DNStemplate from the selected domain name. To remove a template, a userwould first select a domain name in window 1102 and then select one ofthe templates that has been applied to the selected domain name inwindow 1104 (e.g., by clicking on the DNS template). The user would thenclick button 1106 to initiate removal of the DNS template. Removal wouldinvolve host 102 modifying the DNS records for the domain name anddeleting each entry in the DNS record that was created from the selectedDNS template.

Window 1114 displays a listing of templates that are available for useby the user. The available DNS templates may have been previouslycreated by the user (e.g., using the user interface and methods of FIGS.10A and 10B), or, alternatively, the DNS templates may have beendownload or added from another source, such as a DNS templatemarketplace. Using window 1114, a user can select one of the availableDNS templates and then apply the selected DNS template to one or more ofthe user's domain names. For example, the use could select one of theavailable templates in window 1014 and select one of the domain names inwindow 1102. The user could then click button 1110 to apply the selectedDNS template to the selected domain name. Alternatively, having selectedone of the available templates listed in window 1114, the user couldinstead click button 1112 to have that template applied to all domainnames registered to the user (e.g., all the domain names contained inwindow 1102). After clicking button 1112, therefore, the settings fromthe selected DNS template would be applied across all the user's domainnames.

FIG. 12 is a flowchart illustrating an example method 1200 for applyinga DNS template to a domain name. Method 1200 may be executed, forexample, after a user selects one of the domain names in window 1102 ofFIG. 11 and one of the templates listed in window 1114 and thenactivates button 1110 to apply the selected template to the selecteddomain name. In the case that multiple domain names are selected (or, ifthe template is to be applied to all domain names registered by theuser), method 1200 may be executed for each domain name. Method 1200 maybe performed, for example, by host 102.

In step 1052, an identification of the DNS template and the domain nameto which the template is to be applied are received. For example, if theuser has selected one of the templates in window 1114 of FIG. 11, step1052 may involve receiving an identification number or code for theselected template and an identification of the selected domain name.After the identification of the DNS template to be applied is received,in step 1204 the contents of the identified DNS template are retrieved.This may involve, for example, host 102 retrieving the contents of theDNS template from the DNS template database stored in database 107, inwhich a number of different DNS templates may be stored.

After the contents of the DNS template are retrieved, in step 1206 thecontents of the DNS template are analyzed to identify any domain namevariables. If so, those variables are replaced with the domain name towhich the DNS template is to be applied. As mentioned above, theidentification of the domain name is received in step 1202. Inembodiments, where the DNS template includes an ‘@’ character (i.e., acharacter defined by DNS standard to refer to the primary domain nameitself), the ‘@’ character may be left intact and processed on the flyto refer to the domain name to which the DNS template is to be applied.

To illustrate, a DNS template may include the following entries:

[domain name]. IN NS ns [domain name]. IN NS ns.somewhere.example.com.www IN CNAME [domain name]. wwwtest IN CNAME www

If the domain name to which the DNS template is being applied ismikes-bikes.com′, step 1206 would involve replacing each of thevariables ‘[domain name]’ with the domain name ‘mikes-bikes.com’. Assuch, in this example, after performing step 1206 the contents of theDNS template would be as follows:

mikes-bikes.com. IN NS ns

mikes-bikes.com. IN NS ns.somewhere.example.com. www IN CNAMEmikes-bikes.com. wwwtest IN CNAME www

In step 1208, host 102 determines whether the DNS template includes anysettings setting forth MX records. If so, host 102 removes anypre-existing MX records for the domain name to which the DNS template isto be applied. This step ensures that if the DNS template does containMX records they don't conflict with any existing MX records that mayalready exist for the domain name. Before removing the pre-existing MXrecords, the user may be presented with a warning and asked forconfirmation for host 102 to proceed with the removal of thepre-existing MX records.

In step 1210, the records from the DNS template (following the insertionof the domain name in step 1206) are inserted into the DNS record forthe domain name. The updated DNS record could then be made live for thedomain name so that the new settings get promulgated out into the DNS.Or, alternatively, the user could be presented with a confirmationscreen showing the new domain name DNS settings following application ofthe DNS template. Then, if the settings appear to be correct, the usercan confirm that the changes should be implemented, at which time thesettings will go live.

During the execution of step 1210, host 102 may be configured todetermine whether any of the settings specified in the DNS template willconflict with any of the existing DNS settings for the domain name. Forexample, host 102 may determine whether the a setting in the DNStemplate is attempting to change a pre-existing DNS setting (e.g., aCNAME or MX record). If so, host 102 could provide the user with awarning than an existing record is being changed and ask the user toconfirm that the change should be made. Alternatively, if no conflict isdetected, host 102 may implement the change automatically.

In some embodiments, if a conflict is identified, the user may beprompted to indicate whether the existing setting or the new settingtaken from the DNS template is to take precedence. In which case, therecord that takes precedence with be entered into the DNS record for thedomain name and the other record will either be deleted or not added tothe DNS record.

At the completion of method 1200, host 102 may store a record indatabase 107 indicating that the selected DNS template has been appliedto the domain name. This record can then be utilized when displayinguser interface 1100 to identify, for a particular domain name, which DNStemplates have been applied or are active as shown in window 1104.

Once a DNS template has been applied to a domain name, the DNS settingscreated from the DNS template can be locked so that they cannot beedited or otherwise modified by the user. In that case, when the userattempts to manually edit the DNS record for a domain name any settingsthat were generated via a DNS template may be uneditable, preventing anychanges. In that case, the user will only be able to remove the DNStemplate, thereby deleting any DNS settings that were created by thetemplate.

As mentioned above, a user may elect to create a DNS template using anexisting DNS record for one of the user's domain names. In otherembodiments, however, DNS templates may be published by third partiesand made available for download by the user. In this manner, the usercan download and utilize DNS templates created by third parties. Such animplementation may be useful, for example, to allow companies or onlineservice providers to provide DNS templates that include a number ofsettings configured specifically for their online services enablingusers to quickly and easily configure their own domain names to workwith those services.

For example, a service provider that provides online email servicescould distribute a DNS template that includes a number of MX settings.Users that wish to utilize the company's email services could simplyinstall that DNS template into the DNS record for their domain name touse the service provider's email services.

In another example, a company that provides a suite of online servicescould distribute a DNS template that include a comprehensive set ofsettings to configure a domain name to utilize the company's nameservers, email servers, and other online services.

When generating a DNS template to be distributed to other users, the DNStemplate could be created in a similar manner to that depicted by themethod of FIG. 10B. As such, a company wishing to distribute a DNStemplate could access their own DNS records and select a subset of DNSsettings to be incorporated into a DNS template. Alternatively, the DNStemplate could be constructed by hand, or using a tool or softwareapplication to facilitate the creation of a DNS template.

Once created, the DNS templates could be distributed to the other usersvia a DNS template marketplace. Once uploaded to the marketplace, a usercould access the DNS template marketplace to browse available DNStemplates, read about the contents of the DNS templates, and select oneor more of the available DNS template for download or purchase.

FIG. 13 is a screenshot depicting an example user interface 1300enabling a user to browse a number of available DNS templates via a DNStemplate marketplace. After a user provides authentication credentials,host 102 can display user interface 1300, which provides a number ofdisplay options and content that are tailored to the user.

As illustrated, user interface 1300 includes window 1302 that lists anumber of DNS templates that are recommended for the user. Theidentification of the DNS templates that are recommended could be basedupon any suitable factors.

For example, host 102 may have a record of a user account of the userthat indicates the user has signed up for a particular third partyservice. In that case, if the company operating that third party servicehas published a DNS template within the marketplace, that DNS templatecould be listed as a “Recommended For You” DNS template. For example,the user's user account may indicate that the user wishes to utilize athird party email service provider. In that case, if the email providerhas published a DNS template on the marketplace (e.g., a DNS templatethat includes a number of MX settings specifically configured to enableemail services via the email provider), then that DNS template could berecommended to the user.

In other cases, the user's user account with host 102 may indicate thatthe user is operating a particular type of website. In that case, therecommendation of particular DNS templates could be based upon the typeof website. For example, if the user is hosting a personal blog website,the recommended DNS templates could include those likely to be helpfulto someone operating a personal website. Example DNS templates couldinclude DNS templates, for blogging services, photo sharing services,and the like.

However, if the user account indicates that the user is operating abusiness website, the recommend DNS templates could include those thatmay be useful to a small business owner, for example, Example DNStemplate could include those from companies providing email services,small business software services, online accounting services, and thelike.

In still other cases, the DNS templates that are recommended to the usercould be recommend at least partially based upon the location of theuser as well as the location of the service provider associated with thetemplates. The user's location could be determined by host 102 basedupon information contained within the user's user account or via areverse IP address lookup or any other suitable mechanism. The serviceprovider could similarly provide their own location as part of the DNStemplate upload process, or the location could be derived from an IPaddress of the service provider or an IP address contained within theiruploaded DNS template. In that case, DNS templates may be recommendedfor service providers that are located nearby the user or within aparticular geographical region encompassing the user.

User interface 1300 may also include window 1304 that displays a listingof popular DNS templates that can be retrieved from the marketplace. Thepopularity of a particular DNS template could be determined by thenumber of times the DNS template has been downloaded or purchased in thelast 24 hours, last week, last month, or over some other time period.The ordering of templates displayed in either windows 1302 or 1304 couldalso be determined based upon the reviews and rankings of the DNStemplates that have been provided by other users that have installed andutilized the DNS templates.

As in the case of recommended templates, the listing of populartemplates could be limited to showing templates that are popular withina particular geographical region that encompasses the location of theuser.

Using user interface 1300, a user can select one of the DNS templatesshown in either window 1302 (Recommended For You) or window 304(Popular) to view additional details about the selected DNS template.

In the example depicted in FIG. 13, the user has selected one of thetemplates in window 1302 with the title “Small Business Suite—Mail andWeb Settings”, as indicated by selection graphic 1306.

One the user has selected one of the available DNS templates, detailsabout the DNS template can be displayed in window 1308. In variousembodiments, the details include text and can be provided by the entitythat created and distributed the DNS template. Generally, the detailswill include a description of the contents of the DNS templates. In somecases, user may submit comments or reviews of a particular DNS template,which may be uploaded to the DNS template marketplace. If any commentshave been submitted for the selected DNS template, the comments can bedisplayed in window 1310.

User interface 1300 also includes a search box 1312 enabling a user tosearch for a desired DNS template.

In some cases, a DNS template in the DNS template marketplace may onlybe accessible to a limited number of users. For example, a company mayonly make their DNS template available to paying customers. In thatcase, if the user is not a paying customer of the company's product, theuser will not see the company's DNS template in the DNS templatemarketplace. Instead, the user must first pay for the company's productand only then will the company's DNS template be available to the userfor download.

Alternatively, some DNS templates may only be accessible to a particularclass of users. For example, a set of DNS templates may only beaccessible to user's that have a classification of ‘professional’ users(e.g., as specified in the user's user account with host 102), whereasnormal non-professional users would not see those DNS templates.

In some cases, the entity uploading a DNS template to the marketplacemay specify a price for the DNS template. In that case, before a usercan download and utilize the DNS template, they must pay the price setby the uploading entity.

In other embodiments, an uploaded DNS template may be vetted forsecurity considerations before being made available via the DNS templatemarketplace. This vetting may involve a manual review of all uploadedDNS templates to ensure that the templates do not create settings to,for example, surreptitiously send network traffic to a nefariousaddress. In some cases, only DNS templates that have been installed bymore than a given number of users may undergo this vetting processbefore being made generally available.

Once the user utilizing user interface 1300 has identified a desired DNStemplate, the user can selected the DNS template and then purchase ordownload the template. With reference to FIG. 13, the user could selectone of the DNS templates in either of windows 1302 or 1304 and thenutilize one of buttons 1314 or 1316 to either download the DNS templateor, if there is a cost associated with the selected DNS template,purchase the DNS template.

Once the selected DNS template is downloaded or purchased, the DNStemplate will appear as an available template for the user, for example,in window 1114 of user interface 1100 of FIG. 11. The user can thenapply the DNS template to one the DNS records of one or more of theuser's registered domain names.

In some embodiments, user interface 1300 may also include a listing ofthe user's registered domain names. In that case, the user could selectone or more of the domain names in user interface 1300 and then beprovided with an option to apply the downloaded or paid-for DNS templatedirectly to the selected domain names.

When a DNS template is changed or modified, the present system isconfigured to identify all (or a subset of) the domain names for whichthe DNS template was installed, and make corresponding changes to theDNS records of those domain names. In this manner, a company thatdistributes a DNS template can issue updates or modifications that willbe propagated out to all of the domain names using the template. Forexample, if a company issues a DNS template with a first set of DNSsettings, which is ultimately installed by thousands of users, beginsusing a new IP address for a particular service, or wishes to changesome other records, they would simply modify their own DNS template.That change would then automatically be distributed to the DNS recordsassociated with each domain name using the DNS template.

FIG. 14 is a flowchart illustrating a method 1400 for updating a DNStemplate and distributing those changes to the DNS records of a numberof domain names. Method 1400 may be executed, for example, by host 102.

In step 1402 a request to change a DNS template is received. The changerequest may identify a specific setting or value in the DNS template tobe change, or may involving replacing the DNS template with an entirelynew DNS template.

In step 1404, the requester of the change is identified andauthenticated to ensure that the requester has sufficient permission tochange the DNS template. This may, for example, involve prompting therequester to provide a username and password as authentication. If theuser is authenticated, host 102 can confirm that the username is on alist of usernames authorized to make changes to the DNS template.

Once the requester is authenticated and confirmed to have sufficientpermission to modify the DNS template, in step 1406, the DNS template ismodified in accordance with the original request. As described above,the DNS templates may be stored in database 107. As such, step 1406 mayinvolve accessing database 107 to modify the values of a DNS templatepursuant to the request. This step may also involve a vetting process,whereby any changes made to a DNS template can be reviewed to ensure thechanges to not create security concerns. This vetting may involve amanual review of all uploaded DNS templates to ensure that the templatesdo not create settings to, for example, surreptitiously send networktraffic to a nefarious address. In some cases, only DNS templates thathave been installed by more than a given number of users may undergothis vetting process before being made generally available.Alternatively, the vetting process may only be undertaken for changesthat are considered significant. In one embodiment, changes to the lastone or two digits of an IP address may be considered a minor change notrequiring security review. But, a change to the first one or two digitsof an IP address may be considered a major change requiring review.

After the DNS template has been modified, in step 1408 host 102identifies a set of N domain names to which the DNS template has beenapplied. As discussed above, when a user applies a template to a domainname, host 102 creates a record in database 107 indicating that the DNStemplate has been applied. These records may be utilized in step 1408 toidentify the set of domain names.

Once the set of domain names has been identified, method 1400 enters aloop that iterates through each of the set of N domain names and appliesthe updated settings from the DNS template to each domain name.

Accordingly, in step 1410 a counter n is set to a value of 1. Then, instep 1412, the updated DNS template is applied to the first domain namein the set of domain name. The application of the updated DNS templatesettings may be performed in a similar manner to the method illustratedin FIG. 12.

Namely, the contents of the updated DNS template are retrieved. This mayinvolve, for example, host 102 retrieving the contents of the updatedDNS template from database 107. After the contents of the updated DNStemplate have been retrieved, the contents of the updated DNS templateare analyzed to identify any domain name variables. If any domain namevariables are present, those variables are replaced with the domain nameto which the updated DNS template is being applied.

Then, host 102 determines whether the updated DNS template includes anysettings setting forth MX records. If so, host 102 removes anypre-existing MX records for the domain name to which the updated DNStemplate is to be applied. This ensures that if the updated DNS templatedoes contain MX records they don't conflict with any existing MX recordsthat may already exist for the domain name.

Finally, the records from the updated DNS template (followingreplacement of the domain name variables with the domain name) areinserted into the DNS record for the domain name. The updated DNS recordcould then be made live for the domain name so that the new settings getpromulgated out into the DNS. Or, alternatively, the changes may not befully implemented until the user is notified of the change and confirmsthat the change should be implemented. For example, the user may beprovided with a confirmation email or any other electronic messageinforming the user that the DNS template has been changed and requestingthe user confirm that the updated DNS template should be installed ontothe user's domain name. If the user confirms that the installationshould proceed, the settings will go live.

During the installation of the updated DNS template, host 102 may beconfigured to determine whether any of the settings specified in theupdated DNS template will conflict with any of the existing DNS settingsfor the domain name.

In some embodiments, if a conflict is identified, the user may beprompted to indicate whether the existing setting or the new settingtaken from the updated DNS template is to take precedence. In whichcase, the record that takes precedence with be entered into the DNSrecord for the domain name and the other record will either be deletedor not added to the DNS record.

After the updated DNS template settings are applied in step 1412, thecounter n is incremented in step 1416. Then, in step 1416 host 102determines when n is less than or equal to the value of N. If so, thereremain a number of domain names to which the updated DNS template shouldbe applied and the method will repeat steps 1412, 1414, and 1416. Ifnot, all domain names using the updated DNS template have been updatedand the method ends as step 1418.

In various embodiments, the present DNS template can be utilized in thecreation of a backup or ‘snapshot’ of a number of DNS settingsassociated with a domain name.

As discussed above, a mistake in the DNS settings for a domain name cancause services hosted at the domain name to be unavailable for as longas 48 hours (24 hours to distribute the error through the DNS, detectthe problem, and an additional 24 hours to distribute the correct DNSsettings).

Given the importance of accurate DNS settings, the present system canstore a number of snapshots of a domain name's DNS settings in the formof a number of different DNS templates. Should an error be detected inthe DNS settings for the domain name, the snapshots allow a user toquickly and easily revert the domain name's DNS settings to a priorstate, potentially correcting an error inadvertently introduced into theDNS settings. In one embodiment, the snapshot may be a data storage filecontaining one or more of the DNS settings for the domain name that werein place in the DNS at the time the snapshot was created. The snapshotmay be a conventional text record (either a text file or a text recordstored in a database) and may be formatted in accordance withconventional formatting requirements for DNS records or zone files. Inother embodiments, however, the snapshots may be stored using anysuitable file or database storage format and/or markup language. Oncecreated, the snapshot can be stored in a suitable data storage device,such as a database 107. The snapshots can then later be retrieved as abackup copy of the DNS record to revert the settings back to a priorstate.

FIG. 15A is a flowchart illustrating a method for creating DNS settingsnapshot in accordance with the present disclosure. Method 1500 may beperformed, for example, by host 102 to create a snapshot of DNS settingsassociated with a domain name where the DNS settings are containedwithin a DNS record in DNS records database 104.

In step 1502, host 102 detects a DNS record trigger event for a DNSrecord associated with a domain name. The trigger event may include, forexample, an initiation of a change to one or more of the settingsassociated with the DNS record. The change may be initiated, forexample, by a user modifying one or more of the DNS settings via asuitable user interface, such as a domain name control panel, or othertool. Alternatively, the change may be initiated by a third partyservice. For example, the change may be introduced due to a userapplying settings from a downloaded DNS template to the DNS record of adomain name. In additional to changes to the DNS record, a trigger eventmay include an explicit request to create a snapshot of the DNSsettings. The request may come directly from the user requesting thatthe snapshot be created. Alternatively, the request to create thesnapshot may come from a third party. For example, a user may work withcustomer service agents of their hosting provider for assistance inmaking one or more changes to the DNS settings associated with aparticular domain name. In that case, before making any changes to theDNS settings on behalf of the user, the customer service agent maymanually initiate creation of a snapshot of the DNS settings beforemaking any changes. That snapshot could then be used to revert the DNSsettings to the set of settings that were in existence before thecustomer service agent made any changes. In those cases, the explicitrequest for the creation of a snapshot constitutes the trigger event ofstep 1502.

In step 1504, after detecting the trigger event, a snapshot of the DNSrecord associated with the domain name is created. This may involve, forexample, creating a DNS template for all DNS settings associated withthe domain name. In one example, the snapshot may be created as a DNStemplate according to the method depicted in FIG. 10B and described inthe corresponding written description, above. In other embodiments,however, because the snapshot serves as a backup to a specific domainname, there may be no requirement that the domain name itself bestripped from the DNS template. In that case, if the DNS template iscreated according to the method of FIG. 10B, there may be no requirementfor the performance of steps 1054 and 1056.

In some embodiments, the snapshot includes copies of all DNS settings ineffect at the time the snap shot is created. In other embodiments,however, the snapshot may only store the settings that have beenchanged—this presumes that the trigger event for the creation of thesnapshot is an initiation of a change to the record.

In step 1506, after the snapshot has been created, the snapshot isstored for later retrieval. As mentioned above, the snapshot may bestored in any suitable data storage device, such as database 107.

In some embodiments, when the trigger event is a manual change beingmade to the DNS record, the user making the change may be prompted toprovide a description of the change. This description could allow theuser to describe why the change was being made, potentially assisting auser in later understanding why a particular snapshot was created.Additionally, the time and date at which a snapshot was created may alsobe stored in conjunction with the snapshot.

Once the snapshot has been created, a user can access a listing ofpreviously-stored snapshots for a domain name registered to the user.The user can then select one of the snapshots and cause the DNS settingsfor the domain name to be reverted back to the settings associated withthe snapshot.

To illustrate, FIG. 16 is a screenshot depicting an example userinterface enabling a user to select a snapshot containing DNS settingsand apply those settings to the domain name. In the example shown inFIG. 16, the user interface is displaying a listing of availablesnapshots for the domain name ‘example.com’. In this example it isassumed that the user has sufficient permissions to modify the DNSrecords associated with the domain name ‘example.com’. For example, userinterface 1600 may be displayed on a domain name management website thatrequires a user to provide a username and password and be authenticatedbefore being granted access to the DNS settings for a particular domainname.

As illustrated, interface 1600 identifies a number of snapshots 1602that have been stored for the domain name. Displayed with each snapshot1602 is the date and time at which the snapshot was created as well asany description that was provided by the user making the change thatcaused the snapshot to be created.

If the user wishes to revert the DNS settings for the domain name‘example.com’ to an earlier set of settings, the user selects one of thesnapshots 1602 using one of user interfaces 1604 (in this examplecheckboxes, though any suitable user interface may be utilized). After asnapshot 1602 is selected, the user clicks button 1606. After clickingbutton 1606 the system retrieves the contents of the selected snapshot1602 and reverts the DNS settings associated with the domain name‘example.com’ to those defined in the selected snapshot.

Although the descriptions supplied by the user can be useful in helpingselect the appropriate snapshot, in some embodiments the system may beconfigured to store additional information when a snapshot is created tofurther aid a user in selecting the correct desired snapshot whenreverting the DNS settings for a domain name.

For example, FIG. 15B is a flowchart illustrating method 1550 forcreating a snapshot in which additional diagnostic data is stored withthe snapshot. The diagnostic data can be used to identify with moreprecision a prior snapshot (e.g., where the supplied description is notsufficiently precise). The diagnostic information may also be used todiagnose problems in the DNS settings.

In the present disclosure, method 1550 is described as an extension tomethod 1500 described above. Accordingly, method 1550 includes steps1502, 1504, and 1506, described above with respect to method 1500.

After the snapshot has been created in step 1504, in step 1552 therequested changes are analyzed to identify each setting that is beingchanged. This may involve both new settings, as well as existingsettings in which one or more value has been changed.

For each change, an IP address or hostname that makes up the value ofthe changed settings is identified. To illustrate, in the followingrecord, the value is the hostname ‘destination.com’.

mikes-bikes.com. IN NS destination.com.

And in the following record, the value is the IP address 192.168.0.4.

accounts IN A 192.168.0.4

Having identified IP addresses and hostnames present for each change inthe DNS settings, in step 1554 the status of each IP address andhostname is tested. This may involve, for example, pinging each IPaddresses do determine whether the IP address points to a host or serverthat is responsive to the ping request. In other embodiments, anysuitable technique (e.g., NSLOOK, HTTP/HTTPS tests, etc.) fordetermining whether an active host or server is present at the IPaddress may be utilized. The testing can determine whether the IPaddress or hostname points to a server accessible via the Internet. Ifno active host or server is identified, the user may be warned that theprovided IP address or hostname does not point to a device accessiblevia the Internet.

After the IP addresses and domain names associated with each recordchange have been analyzed to determine whether they point to accessiblehosts on the Internet, in step 1506 the snapshot is stored (this stepmay be substantially similar to the step 1506 in method 1500), anddiagnostic data is also stored in 1556. The diagnostic data indicates,for each change, whether the change is associated with an IP address ordomain name that is accessible via the Internet. This diagnosticinformation can be stored, for example, in database 107 in conjunctionwith the snapshot data stored in step 1506.

Having stored the diagnostic data in association with the snapshot, auser can access a listing of previously-stored snapshots for a domainname registered to the user and review both the description anddiagnostic data associated with each snapshot. The user can then selectone of the snapshots and cause the DNS settings for the domain name tobe reverted back to the settings associated with the selected snapshot.

To illustrate, FIG. 17 is a screenshot depicting an example userinterface enabling a user to select a snapshot containing DNS settingsin which additional diagnostic data is displayed. In the example shownin FIG. 17, the user interface is displaying a listing of availablesnapshots for the domain name ‘example.com’. In this example it isassumed that the user has sufficient permissions to modify the DNSrecords associated with the domain name ‘example.com’. For example, userinterface 1700 may be displayed on a domain name management website thatrequires a user to provide a username and password and be authenticatedbefore being granted access to the DNS settings for a particular domainname.

As illustrated, interface 1700 identifies a number of snapshots 1702that have been stored for the domain name. Displayed with each snapshot1702 is the date and time at which the snapshot was created as well asany description that was provided by the user making the change thatcaused the snapshot to be created. Additionally, any diagnostic dataassociated with each snapshot is also presented. As described above, thediagnostic data provides an indication of whether the IP addresses anddomain names associated with a record change pointed at the time of thechange to accessible hosts on the Internet.

If the user wishes to revert the DNS settings for the domain name‘example.com’ to an earlier set of settings, the user selects one of thesnapshots 1702 using one of user interfaces 1704 (in this examplecheckboxes, though any suitable user interface may be utilized). After asnapshot 1702 is selected, the user clicks button 1706. After clickingbutton 1706 the system retrieves the contents of the selected snapshot1702 and reverts the DNS settings associated with the domain name‘example.com’ to those defined in the selected snapshot.

In one implementation a method includes receiving, by at least oneserver communicatively coupled to a network, a request from a user tocreate a custom domain name link to a third party service. The requestidentifies a custom domain name and the third party service. The methodincludes accessing, by the at least one server, a third party servicelink database to identify an entry for the third party servicespecifying either a uniform resource locator (URL) redirect-based customdomain name link or a domain name system (DNS)-based custom domain namelink, and, when the entry specifies the URL redirect-based custom domainname link for the third party service, creating, without further inputfrom the user, a first DNS entry pointing the custom domain name to aweb server accessible to the at least one server, and creating, on theweb server, a URL redirect to redirect Internet traffic directed to thecustom domain name to the third party service. The method includes, whenthe entry specifies the DNS-based custom domain name link for the thirdparty service, creating, without further input from the user, a secondDNS entry pointing the custom domain name to the third party service,and causing the third party service to create a custom domain namemapping that maps the custom domain name to a user account of the user.

In another implementation, a method includes receiving, by at least oneserver communicatively coupled to a network, a request from a user tocreate a custom domain name link to a third party service. The requestidentifies a custom domain name and the third party service. The methodincludes retrieving, by the at least one server, from a third partyservice link database an entry for the third party service specifyinghow to create the custom domain name link for the third party service,and creating, by the at least one server, the custom domain name link inaccordance with the entry retrieved from the third party service linkdatabase.

In another implementation, a system includes a third party service linkdatabase storing, for each of a plurality of third party services, atleast one entry specifying either a uniform resource locator (URL)redirect-based custom domain name link or a domain name system(DNS)-based custom domain name link. The system includes a processorconfigured to perform the steps of receiving, by at least one servercommunicatively coupled to a network, a request from a user to create acustom domain name link to a third party service, the requestidentifying a custom domain name and the third party service, accessing,by the at least one server, the third party service link database toidentify an entry for the third party service, when the entry specifiesthe URL redirect-based custom domain name link for the third partyservice, creating, without further input from the user, a first DNSentry pointing the custom domain name to a web server accessible to theat least one server, and creating, on the web server, a URL redirect toredirect Internet traffic directed to the custom domain name to thethird party service, and, when the entry specifies the DNS-based customdomain name link for the third party service, creating, without furtherinput from the user, a second DNS entry pointing the custom domain nameto the third party service, and causing the third party service tocreate a custom domain name mapping that maps the custom domain name toa user account of the user.

In another embodiment a system includes a DNS template databaseconfigured to store DNS templates, a DNS record database configured tostore a plurality of DNS records for a plurality of domain names, and ahost computer server. The host computer server is configured to receivean electronic signal encoding a request to create a DNS template from auser. The request identifies a domain name. The host computer server isconfigured to access the DNS record database to retrieve a DNS recordfor the domain name identified in the request, parse the DNS record intoa plurality of DNS settings, display the plurality of DNS settings on auser interface for the user, receive, via the user interface, aselection of at least one of the DNS settings by the user, construct aDNS template using the selection of the at least one of the DNSsettings, and store the DNS template in the DNS template database.

In another embodiment, a system, includes a DNS template databaseconfigured to store DNS templates, a DNS record database configured tostore a plurality of DNS records for a plurality of domain name, and ahost computer server. The host computer server is configured receive anelectronic signal encoding a request to apply a DNS template to a domainname from a user. The request identifies the domain name. The hostcomputer server is configured to access the DNS template database toretrieve the DNS template identified in the request, and at least one ofmodify and create a record in the DNS record database to insert settingsfrom the DNS template into a DNS record for the domain name.

In another embodiment, a method includes receiving an electronic signalencoding a request to create a DNS template from a user. The requestidentifies a domain name. The method includes accessing a DNS recorddatabase to retrieve a DNS record for the domain name identified in therequest, parsing the DNS record into a plurality of DNS settings,displaying the plurality of DNS settings on a user interface for theuser, receiving, via the user interface, a selection of at least one ofthe DNS settings by the user, constructing a DNS template using theselection of the at least one of the DNS settings, and storing the DNStemplate in a DNS template database.

In another embodiment, a system includes a DNS template databaseconfigured to store DNS templates, a DNS record database configured tostore a plurality of DNS records for a plurality of domain names, and ahost computer server. The host computer server is configured to receivean electronic signal encoding a request containing a modification to aDNS template from a user. The DNS template is stored in the DNS templatedatabase. The host computer server is configured to access the DNStemplate database to modify the DNS template according to requestcontaining the modification to create a modified DNS template, identifya plurality of domain names using the DNS template, and, for each domainname in the plurality of domain names, access the DNS record database toat least one of modify and create a DNS record for the domain name usingthe modified DNS template.

In another embodiment, a system includes a DNS template databaseconfigured to store DNS templates, a DNS record database configured tostore a plurality of DNS records for a plurality of domain names, and ahost computer server. The host computer server is configured to receivean electronic signal encoding a request containing a modification to aDNS template from a user. The DNS template is stored in the DNS templatedatabase. The host computer server is configured to identify a domainname using the DNS template, and access the DNS record database to atleast one of modify and create a DNS record for the domain name usingthe DNS template based upon the request.

In another embodiment, a method includes receiving an electronic signalencoding a request containing a modification to a DNS template from auser. The DNS template is stored in a DNS template database. The methodincludes accessing the DNS template database to modify the DNS templateaccording to request containing the modification to create a modifiedDNS template, identifying a plurality of domain names using the DNStemplate, and, for each domain name in the plurality of domain names,accessing the DNS record database to at least one of modify and create aDNS record for the domain name using the modified DNS template.

In another embodiment, a system includes a DNS record databaseconfigured to store a plurality of DNS records for a plurality of domainname, and a host computer server. The host computer server is configuredto detect a change in a DNS record for a domain name, upon detecting thechange in the DNS record, encode, without any user input, at least oneDNS setting from the DNS record for the domain name into a data storagefile, prompt a user to provide a description, and store the data storagefile containing the at least one DNS setting in a database inassociation with the description.

In another embodiment, a system includes a DNS record databaseconfigured to store a plurality of DNS records for a plurality of domainname, and a host computer server. The host computer server is configuredto receive an electronic signal encoding a request to create a snapshotof a DNS record for a domain name, encode, in response to the request,at least one DNS setting from a DNS record associated with the domainname in the DNS record database into a data storage file, prompt a userto provide a description, and store the data storage file containing theat least one DNS setting in a database in association with thedescription.

In another embodiment, a method includes detecting a change in a DNSrecord for a domain name, upon detecting the change in the DNS record,encoding, without any user input, at least one DNS setting from the DNSrecord for the domain name into a data storage file, prompting a user toprovide a description, and storing the data storage file containing theat least one DNS setting in a database in association with thedescription.

Various embodiments of the present invention may be embodied in manydifferent forms, including, but in no way limited to, computer programlogic for use with a processor (e.g., a microprocessor, microcontroller, digital signal processor, server computer, or generalpurpose computer), programmable logic for use with a programmable logicdevice (e.g., a Field Programmable Gate Array (FPGA) or other PLD),discrete components, integrated circuitry (e.g., an Application SpecificIntegrated Circuit (ASIC)), or any other means including any combinationthereof.

Computer program logic implementing all or part of the functionalitypreviously described herein may be embodied in various forms, including,but in no way limited to, a source code form, a computer executableform, and various intermediate forms (e.g., forms generated by anassembler, compiler, linker, or locator). Source code may include aseries of computer program instructions implemented in any of variousprogramming languages (e.g., an object code, an assembly language, or ahigh-level language such as C, C++, or JAVA) for use with variousoperating systems or operating environments. The source code may defineand use various data structures and communication messages. The sourcecode may be in a computer executable form (e.g., via an interpreter), orthe source code may be converted (e.g., via a translator, assembler, orcompiler) into a computer executable form.

The computer program may be fixed in any form (e.g., source code form,computer executable form, or an intermediate form) in a tangible storagemedium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM,EEPROM, or Flash-Programmable memory), a magnetic memory device (e.g., adiskette or fixed disk), an optical memory device (e.g., a CD-ROM), a PCcard (e.g., PCMCIA card), or other memory device. The computer programmay be distributed in any form as a removable storage medium withaccompanying printed or electronic documentation (e.g., shrink wrappedsoftware), preloaded with a computer system (e.g., on system ROM orfixed disk), or distributed from a server or electronic bulletin boardover the communication system (e.g., the Internet or World Wide Web).

Hardware logic (including programmable logic for use with a programmablelogic device) implementing all or part of the functionality previouslydescribed herein may be designed using traditional manual methods, ormay be designed, captured, simulated, or documented electronically usingvarious tools, such as Computer Aided Design (CAD), a hardwaredescription language (e.g., VHDL or AHDL), or a PLD programming language(e.g., PALASM, ABEL, or CUPL).

Programmable logic may be fixed either permanently or temporarily in atangible storage medium, such as a semiconductor memory device (e.g., aRAM, ROM, PROM, EEPROM, or Flash-Programmable memory), a magnetic memorydevice (e.g., a diskette or fixed disk), an optical memory device (e.g.,a CD-ROM), or other memory device. The programmable logic may bedistributed as a removable storage medium with accompanying printed orelectronic documentation (e.g., shrink wrapped software), preloaded witha computer system (e.g., on system ROM or fixed disk), or distributedfrom a server or electronic bulletin board over the communication system(e.g., the Internet or World Wide Web).

The present disclosure describes preferred embodiments with reference tothe Figures, in which like numbers represent the same or similarelements. Reference throughout this specification to “one embodiment,”“an embodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “in one embodiment,” “in an embodiment,” andsimilar language throughout this specification may, but do notnecessarily, all refer to the same embodiment.

The described features, structures, or characteristics of the inventionmay be combined in any suitable manner in one or more embodiments. Inthe description, numerous specific details are recited to provide athorough understanding of embodiments of the invention. One skilled inthe relevant art will recognize, however, that the invention may bepracticed without one or more of the specific details, or with othermethods, components, materials, and so forth. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

The schematic flow chart diagrams included are generally set forth aslogical flow-chart diagrams. As such, the depicted order and labeledsteps are indicative of one embodiment of the presented method. Othersteps and methods may be conceived that are equivalent in function,logic, or effect to one or more steps, or portions thereof, of theillustrated method. Additionally, the format and symbols employed areprovided to explain the logical steps of the method and are understoodnot to limit the scope of the method. Although various arrow types andline types may be employed in the flow-chart diagrams, they areunderstood not to limit the scope of the corresponding method. Indeed,some arrows or other connectors may be used to indicate only the logicalflow of the method. For instance, an arrow may indicate a waiting ormonitoring period of unspecified duration between enumerated steps ofthe depicted method. Additionally, the order in which a particularmethod occurs may or may not strictly adhere to the order of thecorresponding steps shown. Some embodiments provided for are describedas computer-implemented method claims. However, one of ordinary skill inthe art would realize that the method steps may be embodied as computercode and the computer code could be placed on a tangible, non-transitorycomputer readable medium defining a computer program product.

Although the above discussion discloses various exemplary embodiments ofthe invention, it should be apparent that those skilled in the art canmake various modifications that will achieve some of the advantages ofthe invention without departing from the true scope of the invention.

The invention claimed is:
 1. A system, comprising: a domain name system(DNS) record database configured to store a plurality of DNS records fora plurality of domain name; and a host computer server, configured to:detect a change in a DNS record for a domain name, upon detecting thechange in the DNS record, encode, without any user input, at least oneDNS setting from the DNS record for the domain name into a data storagefile, prompt a user to provide a description, and store the data storagefile containing the at least one DNS setting in a database inassociation with the description.
 2. The system of claim 1, wherein theat least one DNS setting from the DNS record includes the change in theDNS record.
 3. The system of claim 1, wherein the host computer isconfigured to: retrieve the data storage file and the description fromthe database; and display the description in a user interface enablingthe user to select the description.
 4. The system of claim 1, whereinthe host computer server is configured to: identify an Internet Protocoladdress or hostname in the change in the DNS record; and determinewhether the Internet Protocol address or the hostname identifies anInternet-accessible computer server.
 5. The system of claim 4, whereinthe host computer server is configured to: store an indication ofwhether the Internet Protocol address or the hostname identifies anInternet-accessible computer server in the database in association withthe data storage file.
 6. The system of claim 5, wherein the hostcomputer is configured to: retrieve the data storage file, thedescription, and the indication of whether the Internet Protocol addressor the hostname identifies an Internet-accessible computer server fromthe database; and display the description and the indication in a userinterface enabling the user to select the description.
 7. The system ofclaim 1, wherein the data storage file is formatted as a DNS zone file.8. A system, comprising: a domain name system (DNS) record databaseconfigured to store a plurality of DNS records for a plurality of domainname; and a host computer server, configured to: receive an electronicsignal encoding a request to create a snapshot of a DNS record for adomain name, encode, in response to the request, at least one DNSsetting from a DNS record associated with the domain name in the DNSrecord database into a data storage file, prompt a user to provide adescription, and store the data storage file containing the at least oneDNS setting in a database in association with the description.
 9. Thesystem of claim 8, wherein the host computer is configured to: retrievethe data storage file and the description from the database; and displaythe description in a user interface enabling the user to select thedescription.
 10. The system of claim 8, wherein the host computer serveris configured to: identify an Internet Protocol address or hostname inthe DNS record; and determine whether the Internet Protocol address orthe hostname identifies an Internet-accessible computer server.
 11. Thesystem of claim 10, wherein the host computer server is configured to:store an indication of whether the Internet Protocol address or thehostname identifies an Internet-accessible computer server in thedatabase in association with the data storage file.
 12. The system ofclaim 11, wherein the host computer is configured to: retrieve the datastorage file, the description, and the indication of whether theInternet Protocol address or the hostname identifies anInternet-accessible computer server from the database; and display thedescription and the indication in a user interface enabling the user toselect the description.
 13. The system of claim 8, wherein the datastorage file is formatted as a DNS zone file.
 14. A method, comprising:detecting a change in a domain name system (DNS) record for a domainname; upon detecting the change in the DNS record, encoding, without anyuser input, at least one DNS setting from the DNS record for the domainname into a data storage file; prompting a user to provide adescription; and storing the data storage file containing the at leastone DNS setting in a database in association with the description. 15.The method of claim 14, wherein the at least one DNS setting from theDNS record includes the change in the DNS record.
 16. The method ofclaim 15, including: retrieving the data storage file and thedescription from the database; and displaying the description in a userinterface enabling the user to select the description.
 17. The method ofclaim 14, including: identifying an Internet Protocol address orhostname in the change in the DNS record; and determining whether theInternet Protocol address or the hostname identifies anInternet-accessible computer server.
 18. The method of claim 17,including: storing an indication of whether the Internet Protocoladdress or the hostname identifies an Internet-accessible computerserver in the database in association with the data storage file. 19.The method of claim 18, including: retrieving the data storage file, thedescription, and the indication of whether the Internet Protocol addressor the hostname identifies an Internet-accessible computer server fromthe database; and displaying the description and the indication in auser interface enabling the user to select the description.
 20. Themethod of claim 14, wherein the data storage file is formatted as a DNSzone file.